From 3d511563c0dc877a63553e39de38ad3513c3033a Mon Sep 17 00:00:00 2001 From: "emellor@leeni.uk.xensource.com" Date: Mon, 7 Nov 2005 12:36:35 +0100 Subject: [PATCH] Diagnostic for hitting the nloopbacks limit. This is presumably the cause of all the "two bridges don't work" bugs that have been reported (bug #381). Consideration will be given to raising the default limit -- this is just a diagnostic of the problem. Signed-off-by: Ewan Mellor --- tools/examples/network-bridge | 12 +++++++++--- 1 file changed, 9 insertions(+), 3 deletions(-) diff --git a/tools/examples/network-bridge b/tools/examples/network-bridge index 4330c3332e..b79dcb6b79 100755 --- a/tools/examples/network-bridge +++ b/tools/examples/network-bridge @@ -195,12 +195,18 @@ op_start () { return fi - create_bridge ${bridge} - if ! ip link show 2>/dev/null | grep -q "^[0-9]*: ${vdev}"; then - return + echo " +Link $vdev is missing. +This may be because you have reached the limit of the number of interfaces +that the loopback driver supports. If the loopback driver is a module, you +may raise this limit by passing it as a parameter (nloopbacks=). +" >&2 + exit 1 fi + create_bridge ${bridge} + if ip link show ${vdev} 2>/dev/null >/dev/null; then mac=`ip link show ${netdev} | grep 'link\/ether' | sed -e 's/.*ether \(..:..:..:..:..:..\).*/\1/'` preiftransfer ${netdev} -- 2.30.2